| Purpose |
Carrier Determination if SO Updated |
| Release No |
001 |
| Submitted |
09/27/2013 |
| Submitted by |
Surya Basa |
| Source/Destination Systems |
NED100 to NEQ100 |
| Release Sent To |
Daniel Brennan |
| Object(s) Created By |
Surya Basa |
| Object(s) Tested By |
Surya Basa |
| Transport ID |
Description |
Object Name |
| NEDK921422 |
SD:8729:Update carrier logic for changed sales order |
MV50AFZ1 ZSD_DELIVERY_DEL_TEXT |
| Sl |
Test Scenarios |
Expected Results |
Actual Results |
Doc # |
P/F |
| 1 |
Create delivery for a vendor in the table with a valid record but while creating the sales order manually change the incoterms and carrier which are different from table entries and create the delivery. |
Delivery should be created with the changed value of incoterms and carrier from the sales order. And sales order should not be updated with the table value. |
Delivery updated with the changed value from the sales order and sales order did not updated with the table value. |
65698 80010684 |
P |
| 2 |
Create Delivery for a vendor in the table with a valid record and after creation of delivery document, delete the delivery document and make change in sales order and again create new delivery. |
New delivery should be updated with the changed value from the sales order. |
New delivery updated with the changed value from the sales order. |
65699 80010685 80010686 |
P |
| 3 |
Create a sales order for a vendor in the table with a valid record and after creation of sales order save the sales order and then goto change mode of sales order and make change the incoterms and carrier manually in sales order and save. And create the delivery document. |
The changed value from the sales order should flow to delivery document. |
Delivery updated with the changed value from the sales order. |
65731 80010717 |
P |
| 4 |
Create delivery for a vendor in the table with a valid record and after creation of delivery document, go to sales order again and make changes in incoterms and carrier. |
Existing delivery document should not updated with the changed value from the sales order. |
Existing delivery document did not updated with the changed value from the sales order. |
65732 80010718 |
P |
| Sl |
Test Scenarios |
Expected Results |
Actual Results |
Doc # |
P/F |
| 1 |
Create Delivery for a vendor in the table with a valid record, make sure incoterms and carrier from vendor master are different from table entries. |
Delivery should be created and sales order updated with incoterms and carrier from table. |
Both sales order and delivery document updated with the value maintained in the table. |
65711 80010697 |
P |
| 2 |
Create Delivery for a vendor in the table but without a valid record. |
Delivery should be created with incoterms ROU and carrier 157 (Routing); SO should not be updated. |
Sales order did not update and delivery document updated with default value incoterms ROU and carrier 157. |
65712 80010698 |
P |
| 3 |
Create Delivery for a vendor not in the table. |
Delivery should be created with incoterms and carrier from the sales order. |
Delivery document updated with the value from the sales order. |
65713 80010699 |
P |
| 4 |
Create Delivery for a vendor in the table with multiple valid records. |
Delivery should be created and SO updated with incoterms and carrier from first record in table that matches the delivery weight. |
According to the weight range and first record maintained in the table, both sales order and delivery document got updated. |
65714 80010700 |
P |
| 5 |
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is set when language is EN |
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) should be deleted; SO header text should not be deleted. |
Header text to the delivery document did not flow from the sales order and sales order header text did not delete. |
65716 80010702 |
P |
| 6 |
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is not set when language is EN |
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) should be carried over from Sales Order / Customer Text; SO header text should not be deleted. |
Header text to the delivery document passed from sales order and header text at sales order did not delete. |
65719 80010705 |
P |
| 7 |
Create a delivery with UOM in Kg and table entry in lbs. |
Conversion should work correctly, choosing the correct weight range table entry |
Conversion worked correctly. And as per the weight range matching from the table, the incoterm and carrier updated accordingly to sales order and delivery document. |
65720 80010706 |
P |
| 8 |
Create a delivery with UOM in oz. and table entry in lbs. |
Conversion should work correctly, choosing the correct weight range table entry |
Conversion worked correctly. And as per the weight range matching from the table, the incoterm and carrier updated accordingly to sales order and delivery document. |
65721 80010707 |
P |
| 9 |
Create a delivery with UOM in TON and table entry in Kg. |
Conversion should work correctly, choosing the correct weight range table entry |
Conversion worked correctly. And as per the weight range matching from the table, the incoterm and carrier updated accordingly to sales order and delivery document. |
65722 80010708 |
P |
| 10 |
Create a delivery with a weight of 100 lbs when there are records for 0 - 100 and 100 - 999999 |
Delivery should be created with the incoterms and carrier from the 0 - 100 record |
Sales order and Delivery document updated with the table value related to the weight range 0-100 from table entry. |
65723 80010709 |
P |
| 11 |
Create a delivery with weight of 101 lbs when there are records for 0 - 100 and 100 - 999999 |
Delivery should be created with the incoterms and carrier from the 100 – 999999 record |
Sales order and delivery document updated with the table value related to the weight range 100-999999 from table entry. |
65724 80010710 |
P |
| 12 |
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is set when language is not EN |
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) is deleted; SO header text should not be deleted. |
Header text to the delivery document did not flow from the sales order and sales order header text did not delete. |
65725 80010711 |
P |
| 13 |
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is not set when language is not EN |
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) is carried over from Sales Order / Customer Text; SO header text should not be deleted. |
Header text to the delivery document passed from sales order and header text at sales order did not delete. |
65726 80010712 |
P |
| 14 |
Create a delivery with a weight of 100 lbs when there are records for 0 - 100 and 100 – 999999(both in KG and LB) 0-100—KG and 0-100- LB records are maintained in the table. |
Delivery should be created and SO updated with incoterms and the Customer group 2 of the first matching entry from the table. |
Delivery and sales order updated with the first matching record found from the table. |
65727 80010713 |
P |
| 15 |
Create deliveries via batch to make sure they create correctly |
Deliveries should be created via a batch job with the correct incoterms and carrier based on the table entries and SO's should be updated accordingly. |
Both sales order and delivery document created via batch job and the correct incoterms and carrier based on table entry updated accordingly. |
65701 65702 80010689 80010688 |
P |